docs: container connectivity troubleshooting #346
Conversation
Signed-off-by: JaredforReal <[email protected]>
✅ Deploy Preview for vllm-semantic-router ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
👥 vLLM Semantic Team NotificationThe following members have been identified for the changed files in this PR and have been automatically assigned: 📁
|
JaredforReal
changed the title
|
|
||
| This guide summarizes common connectivity issues we hit when running the router with Docker Compose or Kubernetes and how we fixed them. It also covers the “No data” problem in Grafana and how to validate the full metrics chain. | ||
|
|
||
| ## 1. Use IPv4 addresses for backend endpoints |
There was a problem hiding this comment.
can you check if similar kubernetes networking diagnostics help?
https://goteleport.com/blog/troubleshooting-kubernetes-networking/
There was a problem hiding this comment.
Thanks for sharing the link! I’ve checked it, and while it might be helpful, it doesn’t fully cover the issues I ran into on my lab servers. This PR is based on those practical troubleshooting experiences. Do you think it would make sense to keep both references, so the docs can complement each other?
There was a problem hiding this comment.
Sure, let's keep your inline diagnostics
What type of PR is this?
docs: container connectivity troubleshooting
What this PR does / why we need it:
Add documentation: Container Connectivity Troubleshooting based on practices.
add vsr-headers to
sidebar.ts